Systems and methods for registering 3D data with 2D image data

ABSTRACT

Systems and methods described herein relate to registering three-dimensional (3D) data with two-dimensional (2D) image data. One embodiment receives 3D data from one or more sensors and 2D image data from one or more cameras; identifies a 3D segment in the 3D data and associates it with an object; identifies 2D boundary information for the object; determines a speed and a heading for the object; and registers the 3D segment with the 2D boundary information by adjusting the relative positions of the 3D segment and the 2D boundary information based on the speed and heading of the object and matching, in 3D space, the 3D segment with projected 2D boundary information.

TECHNICAL FIELD

The subject matter described herein relates in general to machine vision and more specifically to systems and methods for registering three-dimensional (3D) data with two-dimensional (2D) image data.

BACKGROUND

An important aspect of robotics is machine vision. For example, autonomous vehicles need to be able to sense the surrounding environment (e.g., roadway, obstacles, etc.) and navigate autonomously without human input or at least partially without human input. In robotics applications such as autonomous vehicles, it is advantageous to combine 2D image data from cameras with 3D data such as point-cloud data from the same scene. Combining these two types of data necessarily includes a registration step to align the points spatially.

SUMMARY

An example of a system for registering 3D data with 2D image data is presented herein. The system comprises one or more sensors to produce 3D data and one or more cameras to produce 2D image data. The system also includes one or more processors and a memory communicably coupled thereto. The memory stores a 3D-data segmentation module including instructions that when executed by the one or more processors cause the one or more processors to identify, in the 3D data, a 3D segment. The memory also stores a data association module including instructions that when executed by the one or more processors cause the one or more processors to associate the 3D segment with an object. The memory also stores an image segmentation module including instructions that when executed by the one or more processors cause the one or more processors to identify 2D boundary information for the object in the 2D image data. The memory also stores a velocity estimation module including instructions that when executed by the one or more processors cause the one or more processors to determine a speed and a heading for the object. The memory also stores an integration module including instructions that when executed by the one or more processors cause the one or more processors to register the 3D segment with the 2D boundary information by performing one of: (1) shifting the 2D boundary information in 2D image space to a position that, based on the object's speed and heading, corresponds to a time at which the 3D data was captured, projecting the time-shifted 2D boundary information into 3D space, and matching the projected time-shifted 2D boundary information with the 3D segment; (2) projecting the 2D boundary information into 3D space, shifting the projected 2D boundary information in 3D space to a position that, based on the object's speed and heading, corresponds to a time at which the 3D data was captured, and matching the time-shifted projected 2D boundary information with the 3D segment; and (3) projecting the 2D boundary information into 3D space, shifting the 3D segment in 3D space to a position that, based on the object's speed and heading, corresponds to a time at which the 2D image data was captured, and matching the projected 2D boundary information with the time-shifted 3D segment.

Another embodiment is a method of registering three-dimensional (3D) data with two-dimensional (2D) image data, comprising receiving 3D data from one or more sensors; receiving 2D image data from one or more cameras; identifying a 3D segment in the 3D data; associating the 3D segment with an object; identifying 2D boundary information for the object in the 2D image data; determining a speed and a heading for the object; and registering the 3D segment with the 2D boundary information by performing one of: (1) shifting the 2D boundary information in 2D image space to a position that, based on the object's speed and heading, corresponds to a time at which the 3D data was captured, projecting the time-shifted 2D boundary information into 3D space, and matching the projected time-shifted 2D boundary information with the 3D segment; (2) projecting the 2D boundary information into 3D space, shifting the projected 2D boundary information in 3D space to a position that, based on the object's speed and heading, corresponds to a time at which the 3D data was captured, and matching the time-shifted projected 2D boundary information with the 3D segment; and (3) projecting the 2D boundary information into 3D space, shifting the 3D segment in 3D space to a position that, based on the object's speed and heading, corresponds to a time at which the 2D image data was captured, and matching the projected 2D boundary information with the time-shifted 3D segment.

Another embodiment is a system for registering 3D data with 2D image data, comprising one or more sensors to produce 3D data and one or more cameras to produce 2D image data. The system also includes one or more processors and a memory communicably coupled thereto. The memory stores a 3D-data segmentation module including instructions that when executed by the one or more processors cause the one or more processors to identify, in the 3D data, a 3D segment, wherein the 3D segment is 3D boundary information that includes one of a convex hull, a voxelization, a non-convex hull, a bounding box, and mesh data. The memory also stores an image segmentation module including instructions that when executed by the one or more processors cause the one or more processors to identify 2D boundary information for an object in the 2D image data, the 2D boundary information including one of a perspective bounding box, a shape estimate, and a shape estimate with an accompanying pose estimate. The memory also stores an integration module including instructions that when executed by the one or more processors cause the one or more processors to project the 2D boundary information into 3D space to produce projected 2D boundary information and perform shape matching between the projected 2D boundary information and the 3D boundary information to register the projected 2D boundary information with the 3D boundary information.

Another embodiment is a method of registering three-dimensional (3D) data with two-dimensional (2D) image data, comprising receiving 3D data from one or more sensors; receiving 2D image data from one or more cameras; identifying a 3D segment in the 3D data, wherein the 3D segment is 3D boundary information that includes one of a convex hull, a voxelization, a non-convex hull, a bounding box, and mesh data; identifying 2D boundary information for an object in the 2D image data, the 2D boundary information including one of a perspective bounding box, a shape estimate, and a shape estimate with an accompanying pose estimate; projecting the 2D boundary information into 3D space to produce projected 2D boundary information; and performing shape matching between the projected 2D boundary information and the 3D boundary information to register the projected 2D boundary information with the 3D boundary information.

BRIEF DESCRIPTION OF THE DRAWINGS

The accompanying drawings, which are incorporated in and constitute a part of the specification, illustrate various systems, methods, and other embodiments of the disclosure. It will be appreciated that the illustrated element boundaries (e.g., boxes, groups of boxes, or other shapes) in the figures represent one embodiment of the boundaries. In some embodiments, one element may be designed as multiple elements or multiple elements may be designed as one element. In some embodiments, an element shown as an internal component of another element may be implemented as an external component and vice versa. Furthermore, elements may not be drawn to scale.

FIG. 1 illustrates one embodiment of a vehicle within which systems and methods disclosed herein may be implemented.

FIG. 2 illustrates one embodiment of a 3D/2D registration system.

FIG. 3 illustrates one example of a camera image as may be captured by a camera, in accordance with an illustrative embodiment of the invention.

FIG. 4 illustrates one example of a point cloud representing the same scene depicted by the camera image of FIG. 3, in accordance with an illustrative embodiment of the invention.

FIG. 5 illustrates a point-cloud cluster of one of the objects in the scene of FIG. 3 and associated 3D boundary information, in accordance with an illustrative embodiment of the invention.

FIG. 6 illustrates an embodiment in which 2D boundary information for objects includes 2D bounding boxes.

FIG. 7 illustrates another embodiment in which 2D boundary information for objects includes perspective bounding boxes.

FIG. 8 illustrates yet another embodiment in which 2D boundary information for objects includes shape estimates.

FIG. 9A illustrates misalignment between a point-cloud cluster and projected 2D boundary information derived from 2D image data captured at a different time.

FIG. 9B illustrates a time-shifted point-cloud cluster aligned with projected 2D boundary information, in accordance with an illustrative embodiment of the invention.

FIG. 10A illustrates misalignment between 3D boundary information and projected 2D boundary information derived from 2D image data captured at a different time.

FIG. 10B illustrates 3D boundary information aligned with time-shifted projected 2D boundary information, in accordance with an illustrative embodiment of the invention.

FIG. 11 is a flowchart of a method for registering 3D data with 2D image data, in accordance with an illustrative embodiment of the invention.

FIG. 12 illustrates another embodiment of a 3D/2D registration system.

FIG. 13 is a flowchart of a method for registering 3D data with 2D image data, in accordance with another illustrative embodiment of the invention.

DETAILED DESCRIPTION

At least two challenges arise with 3D-to-2D (“3D/2D”) registration. First, the 2D image data and the 3D data are not necessarily captured at the same instant in time. Sometimes referred to as the “capture-timing gap” problem, this makes it difficult to match up the 3D and 2D data because of moving objects in the scene. For example, for a difference in capture time of only 50 ms, a vehicle traveling 70 mph travels about 1.56 meters, and a typical vehicle is only 3-5 meters long. Second, the 2D sensors (e.g., cameras) capture image data from a different vantage point than the 3D sensors. Therefore, even if the 2D image data and the 3D data are somehow captured at exactly the same time, there is still parallax error between the two kinds of sensor data.

Systems and methods are presented that overcome the “capture-timing gap” and parallax problems. In one embodiment, 3D data is captured from one or more sensors, and 2D image data is captured from one or more cameras. A 3D segment (e.g., a point-cloud cluster or 3D boundary information derived from a point-cloud cluster) is associated with an object, and the speed and heading of the object is measured. 2D boundary information for the object is identified in the 2D image data. Based on the measured speed and heading of the object, the relative positions of the 2D boundary information and the 3D segment are adjusted to compensate for the different capture times of the 3D data and the 2D image data. Once their relative positions have been adjusted, the 2D boundary information, which has been projected into 3D space, and the 3D segment are matched in 3D space to complete registration.

How the adjustment of relative positions is accomplished depends on the particular embodiment. In one embodiment, the 2D boundary information is shifted in 2D image space to a position that, based on the object's speed and heading, corresponds to a time at which the 3D data was captured, the time-shifted 2D boundary information is then projected into 3D space, and the projected time-shifted 2D boundary information is matched with the 3D segment. In another embodiment, the 2D boundary information is projected into 3D space, the projected 2D boundary information is shifted in 3D space to a position that, based on the object's speed and heading, corresponds to a time at which the 3D data was captured, and the time-shifted projected 2D boundary information is matched with the 3D segment. In yet another embodiment, the 2D boundary information is projected into 3D space, the 3D segment is shifted in 3D space to a position that, based on the object's speed and heading, corresponds to a time at which the 2D image data was captured, and the time-shifted 3D segment is matched with the projected 2D boundary information.

In some embodiments, shape-matching techniques are used to match 3D boundary information with projected 2D boundary information in 3D space. This assists in overcoming the parallax problem discussed above. In still other embodiments, shape matching is used to aid registration of 3D boundary information with projected 2D boundary information without time-shifting the 3D boundary information or the 2D boundary information to correct for the object's motion between the different capture times of the 3D data and the 2D image data.

The techniques described herein have wide application in the field of robotics and machine vision. One example of an environment in which the inventive systems and methods can be implemented is a semi-autonomous or fully autonomous vehicle. This is not the only environment in which the inventive techniques can be applied, however. The inventive techniques can be applied to a variety of other types of robots, as those skilled in the art will recognize. For the sake of illustration, embodiments in the environment of a vehicle are described in detail below.

Referring to FIG. 1, an example of a vehicle 100 is illustrated. As used herein, a “vehicle” is any form of motorized transport. In one or more implementations, the vehicle 100 is an automobile. While arrangements will be described herein with respect to automobiles, it will be understood that embodiments are not limited to automobiles. In some implementations, the vehicle 100 may be any other form of motorized transport that, for example, can operate at least semi-autonomously.

The vehicle 100 also includes various elements. It will be understood that in various embodiments it may not be necessary for the vehicle 100 to have all of the elements shown in FIG. 1. The vehicle 100 can have any combination of the various elements shown in FIG. 1. Further, the vehicle 100 can have additional elements to those shown in FIG. 1. In some arrangements, the vehicle 100 may be implemented without one or more of the elements shown in FIG. 1. While the various elements are shown as being located within the vehicle 100 in FIG. 1, it will be understood that one or more of these elements can be located external to the vehicle 100. Further, the elements shown may be physically separated by large distances.

Some of the possible elements of the vehicle 100 are shown in FIG. 1 and will be described along with subsequent figures. However, a description of many of the elements in FIG. 1 will be provided after the discussion of FIGS. 2-13 for purposes of brevity of this description. Additionally, it will be appreciated that for simplicity and clarity of illustration, where appropriate, reference numerals have been repeated among the different figures to indicate corresponding or analogous elements. In addition, the discussion outlines numerous specific details to provide a thorough understanding of the embodiments described herein. Those skilled in the art, however, will understand that the embodiments described herein may be practiced using various combinations of these elements.

The vehicle 100 includes a 3D/2D registration system 170 that is implemented to perform methods and other functions as disclosed herein relating to registering 3D data with 2D image data. In this description, “registering” 3D data with 2D image data refers to lining up segmented 3D data with 2D boundary information from the same scene that has been projected into 3D space so that the two kinds of data can be used in combination. Vehicle 100 can use this combined 3D and 2D data in performing its autonomous-driving functions (identifying obstacles, etc.).

With reference to FIG. 2, one embodiment of the 3D/2D registration system 170 of FIG. 1 is further illustrated. The 3D/2D registration system 170 is shown as including one or more processors 110 from the vehicle 100 of FIG. 1. Accordingly, the one or more processors 110 may be a part of the 3D/2D registration system 170, the 3D/2D registration system 170 may include one or more separate processors from the one or more processors 110 of the vehicle 100, or the 3D/2D registration system 170 may access the one or more processors 110 through a data bus or another communication path, depending on the embodiment. In one embodiment, the 3D/2D registration system 170 includes a memory 210 that stores a 3D-data segmentation module 220, a data association module 230, an image segmentation module 240, a velocity estimation module 250, and an integration module 260. The memory 210 is a random-access memory (RAM), read-only memory (ROM), a hard-disk drive, a flash memory, or other suitable memory for storing the modules 220, 230, 240, 250, and 260. The modules 220, 230, 240, 250, and 260 are, for example, computer-readable instructions that when executed by the one or more processors 110, cause the one or more processors 110 to perform the various functions disclosed herein.

The 3D/2D registration system 170 receives 2D image data 290 from one or more cameras 126 that are part of sensor system 120. FIG. 3 illustrates one example of a camera image as may be captured by a camera 126 of vehicle 100, in accordance with an illustrative embodiment of the invention. The scene 300 in FIG. 3 includes vehicle 310 and vehicle 320. In this example, vehicles 310 and 320 are presumed to be traveling along the same roadway 330 as vehicle 100 (the “ego vehicle,” not shown in FIG. 3).

The 3D/2D registration system 170 receives 3D data 280 from one or more sensors in sensor system 120. The sensors can include Light Detection and Ranging (LIDAR) sensors (see Element 124 in FIG. 1), a set of stereo cameras, Red Green Blue Depth (RGB-D) sensors, radar sensors (see Element 123 in FIG. 1), or a combination of one or more of these types of sensors or one or more other sensors capable of capturing 3D data. These various types of 3D sensors produce what those skilled in the art refer to as a “point cloud” of a scene. FIG. 4 illustrates one example of a point cloud 400 representing the same scene depicted by the camera image of FIG. 3, in accordance with an illustrative embodiment of the invention.

As shown in FIG. 2, 3D data 280 and 2D image data 290 can be stored in a database 270.

3D-data segmentation module 220 generally includes instructions that cause the one or more processors 110 to identify, in the 3D data received from the one or more sensors discussed above, a 3D segment. (Though this description, for simplicity, is cast in terms of a single 3D segment, in practice 3D-data segmentation module 220 can identify, in parallel, a plurality of 3D segments in a point cloud.) In some embodiments, the 3D segment is a point-cloud cluster. In other embodiments, the 3D segment is 3D boundary information derived from a point-cloud cluster. Examples of 3D boundary information include, without limitation, a convex hull, a voxelization, a non-convex hull, a bounding box (in 3D space), and mesh data. These terms are well known to those skilled in the machine-vision art. For example, a convex hull wholly contains the line segments connecting each of its points, whereas a non-convex hull wholly contains the points but does not necessarily contain every line segment between them.

FIG. 5 illustrates an example of 3D boundary information representing a convex hull 510 of vehicle 320 in scene 300 of FIG. 3. As discussed above, a convex hull is one of several types of 3D boundary information that may be used in various embodiments of the invention.

Data association module 230 generally includes instructions that cause the one or more processors 110 to associate a 3D segment (point-cloud cluster or 3D boundary information) with an object. In some embodiments, the object is one that has previously been tracked by an object-tracking function of vehicle 100. For example, data association module 230 might associate a point-cloud cluster or convex hull with a previously tracked vehicle. In some embodiments, object tracking is performed using primarily or exclusively 2D image data 290. In other embodiments, object tracking is performed using primarily or exclusively 3D data 280. In still other embodiments, a combination of 2D image data and 3D data is used to track objects.

Image segmentation module 240 generally includes instructions that cause the one or more processors 110 to identify, in the 2D image data 290, 2D boundary information for the object discussed above. Examples of 2D boundary information include, without limitation, a simple 2D bounding box, a perspective bounding box (a pseudo-3D bounding box drawn in perspective), a shape estimate (also pseudo-3D boundary information drawn in perspective), and a shape estimate with an accompanying pose estimate. FIGS. 6-8 illustrate examples of, respectively, bounding boxes 610 and 620, perspective bounding boxes 710 and 720, and shape estimates 810 and 820, in accordance with illustrative embodiments of the invention. Image segmentation module 240 can employ a variety of techniques to perform object detection or boundary estimation in 2D image space. One well-known object-detection algorithm is MaskRCNN. That algorithm or other algorithms known to those skilled in the machine-vision art can be employed to produce a shape estimate or contour for an object.

In some embodiments, 3D/2D registration system 170 includes a pose-estimation algorithm that estimates the direction in which an object in 2D image data 290 is oriented. In those embodiments, the pose estimate of the object can be used to aid registration, in 3D space, of a projected shape estimate with a 3D segment. As discussed further below, the 2D boundary information produced by image segmentation module 240 is ultimately projected into 3D space for registration with a 3D segment.

Velocity estimation module 250 includes instructions that cause the one or more processors 110 to analyze sensor data from sensor system 120 to determine a speed and a heading (i.e., a velocity) for the object with which data association module 230 associated a 3D segment and for which image segmentation module 240 identified 2D boundary information. The sensor data used to estimate velocity can include 3D sensor data (e.g., LIDAR, radar, or both), 2D sensor data (e.g., image data from a camera 126), or a combination of these types of data. One advantage of radar is that the Doppler shift can be used to estimate the speed of an object directly. Velocity estimation module 250 passes the speed and heading of the object to integration module 260.

Integration module 260 generally includes instructions that cause the one or more processors 110 to line up and combine (i.e., register) 3D data with 2D image data to produce registered data 295. More specifically, in the embodiments described herein, 2D boundary information for an object is projected into 3D space, and registration of that projected 2D boundary information with a 3D segment corresponding to the object is performed in 3D space.

As discussed above, one challenge in registering 3D data with 2D image data is that the 3D and 2D data are typically not captured at the same time instant (i.e., the 3D and 2D sensors are not synchronized), and the two types of data are not captured from the same vantage point, resulting in parallax error. The “capture-timing gap” problem and a technique to address it are illustrated in FIGS. 9A and 9B for the case of a 3D segment that is a point-cloud cluster and 2D boundary information that is a perspective bounding box. In FIG. 9A, there is noticeable misalignment of the point-cloud cluster 910 of vehicle 320 with the projected perspective bounding box 920. This is due to 3D data 280 and 2D image data 290 being captured at different times. In FIG. 9B, the relative positions of point-cloud cluster 910 and projected perspective bounding box 920 have been adjusted based on the measured speed and heading of the object obtained from velocity estimation module 250, resulting in the approximate alignment, in 3D space, of point-cloud cluster 910 with projected perspective bounding box 920.

Adjustment of the relative positions of a 3D segment such as point-cloud cluster 910 and 2D boundary information such as the projected perspective bounding box 920 can be accomplished in different ways, depending on the embodiment. In one embodiment, integration module 260 shifts the 2D boundary information in 2D image space to a position that, based on the object's speed and heading, corresponds to a time at which the 3D data was captured. Integration module 260 then projects the time-shifted 2D boundary information into 3D space and matches the projected time-shifted 2D boundary information with the 3D segment. In another embodiment, integration module 260 projects the 2D boundary information into 3D space and shifts the projected 2D boundary information in 3D space to a position that, based on the object's speed and heading, corresponds to a time at which the 3D data was captured. Integration module 260 then matches the time-shifted projected 2D boundary information with the 3D segment. In yet another embodiment, integration module 260 projects the 2D boundary information into 3D space and shifts the 3D segment in 3D space to a position that, based on the object's speed and heading, corresponds to a time at which the 2D image data was captured. Integration module 260 then matches the time-shifted 3D segment with the projected 2D boundary information.

Whether the 2D boundary information or the 3D segment is shifted in position depends, in some embodiments, on whether the speed and heading of the object are determined from the 3D data 280 or the 2D image data 290. In these embodiments, the data that gets shifted to correct for the “capture-timing gap” problem is the data from which the speed and heading of the object are determined. For example, in one embodiment in which the speed and heading of the object are determined from the 3D data 280 (e.g., LIDAR and/or radar), the 3D segment is shifted in position in 3D space. In a different embodiment in which the speed and heading of the object is determined from the 2D image data 290, the 2D boundary information is shifted in position. As explained above, this shift can be performed in 2D image space prior to projection into 3D space or after projection into 3D space.

In the particular example illustrated in FIG. 9B, point-cloud cluster 910 has been shifted, based on the measured speed and heading of the object (vehicle 320), to a position corresponding to a time at which the 2D image data was captured.

Another example of the “capture-timing gap” problem and its correction is illustrated in FIGS. 10A and 10B for the case of a 3D segment that is 3D boundary information (in this example, a 3D bounding box) and 2D boundary information that is a perspective bounding box. In FIG. 10A, there is noticeable misalignment of the 3D bounding box 1010 of vehicle 320 with the projected perspective bounding box 1020. This is due to 3D data 280 and 2D image data 290 being captured at different times. In FIG. 10B, the relative positions of 3D bounding box 1010 and projected perspective bounding box 1020 have been adjusted based on the measured speed and heading of the object obtained from velocity estimation module 250, resulting in the approximate alignment, in 3D space, of 3D bounding box 1010 with projected perspective bounding box 1020. Note that, in this particular example, the 2D boundary information is projected into 3D space, and the position of the projected 2D boundary information is then shifted in 3D space to correct for the “capture-timing gap.”

The specific techniques integration module 260 uses to match projected 2D boundary information with a 3D segment vary depending on the embodiment. In some embodiments, a nearest-neighbor matching algorithm is employed. In an embodiment in which the 3D segment is a point-cloud cluster, an algorithm can be employed in which the points in the point-cloud cluster lying within the volume defined by the projected 2D boundary information (e.g., a perspective bounding box) are counted to measure the extent of overlap. In other embodiments, in which the 3D segment is 3D boundary information (e.g., a convex hull), integration module 260 uses one or more 3D shape-matching algorithms. For example, in some embodiments, particularly those in which simple 2D bounding boxes are used for the 2D boundary information, a Kalman-filter-based shape-matching algorithm can be used. In some embodiments in which shape matching is used to register 3D boundary information with projected 2D boundary information, integration module 260 can consider their overlapping volumes to assess the extent of a match. Other shape-matching algorithms include the Hungarian algorithm and the Joint Compatibility Branch and Bound (JCBB) algorithm.

FIG. 11 is a flowchart of a method 1100 for registering 3D data with 2D image data, in accordance with an illustrative embodiment of the invention. Method 1100 will be discussed from the perspective of 3D/2D registration system 170 in FIG. 2. While method 1100 is discussed in combination with 3D/2D registration system 170, it should be appreciated that method 1100 is not limited to being implemented within 3D/2D registration system 170, but 3D/2D registration system 170 is instead one example of a system that may implement method 1100.

At block 1110, 3D/2D registration system 170 receives 3D data 280 from one or more sensors in sensor system 120. The sensors can include LIDAR sensors, a set of stereo cameras, RGB-D sensors, radar sensors, or a combination of one or more of these types of sensors or one or more other sensors capable of capturing 3D data. At block 1120, 3D/2D registration system 170 receives image data 290 from one or more cameras 126 that are part of sensor system 120.

At block 1130, 3D-data segmentation module 220 identifies a 3D segment in the 3D data. In some embodiments, the 3D segment is a point-cloud cluster. In other embodiments, the 3D segment is 3D boundary information derived from a point-cloud cluster. Examples of 3D boundary information include, without limitation, a convex hull, a voxelization, a non-convex hull, a bounding box, and mesh data. At block 1140, data association module 230 associates the 3D segment with an object. In some embodiments, the object is one that has previously been tracked by an object-tracking function of vehicle 100. For example, data association module 230 might associate a point-cloud cluster or convex hull with a previously tracked vehicle.

At block 1150, image segmentation module 240 identifies, in the 2D image data 290, 2D boundary information for the object discussed above. Examples of 2D boundary information include, without limitation, a simple 2D bounding box, a perspective bounding box (a pseudo-3D bounding box drawn in perspective), a shape estimate (also pseudo-3D boundary information drawn in perspective), and a shape estimate with an accompanying pose estimate. Examples of simple 2D bounding boxes, perspective bounding boxes, and shape estimates are illustrated in FIGS. 6-8.

At block 1160, velocity estimation module 250 determines the speed and heading (i.e., the velocity) of the object associated with the 3D segment and the 2D boundary information. The sensor data used to estimate velocity can include 3D sensor data (e.g., LIDAR, radar, or both), 2D sensor data (e.g., image data from a camera 126), or a combination of these types of data. Velocity estimation module 250 passes the speed and heading of the object to integration module 260.

At block 1170, integration module 260 registers the 3D segment with the 2D boundary information by doing one of the following to adjust their positions relative to each other, based on the measured speed and heading of the object obtained from velocity estimation module 250: (1) shifting the 2D boundary information in 2D image space to a position that, based on the object's speed and heading, corresponds to a time at which the 3D data was captured, projecting the time-shifted 2D boundary information into 3D space, and matching the projected time-shifted 2D boundary information with the 3D segment; (2) projecting the 2D boundary information into 3D space, shifting the projected 2D boundary information in 3D space to a position that, based on the object's speed and heading, corresponds to a time at which the 3D data was captured, and matching the time-shifted projected 2D boundary information with the 3D segment; or (3) projecting the 2D boundary information into 3D space, shifting the 3D segment in 3D space to a position that, based on the object's speed and heading, corresponds to a time at which the 2D image data was captured, and matching the projected 2D boundary information with the time-shifted 3D segment. As discussed above, a variety of different matching techniques can be used during registration, depending on the embodiment. The resulting registered data 295 can be stored in database 270.

FIG. 12 illustrates a different embodiment of a 3D/2D registration system 170. This embodiment does not include a data association module 230 or a velocity estimation module 250 because time-shifting based on the measured velocity of an object associated with the 3D segment and the 2D boundary information to correct the “capture-timing gap” is not performed in this particular embodiment. Instead, this embodiment performs shape matching between 3D boundary information (e.g., a convex hull) and any of the following types of 2D boundary information projected into 3D space: a perspective bounding box, a shape estimate, and a shape estimate with an associated pose estimate. Some of the various shape-matching algorithms that can be employed, depending on the embodiment, are discussed above.

In the embodiment of FIG. 12, 3D/2D registration system 170 receives 2D image data 290 from one or more cameras 126 that are part of sensor system 120 and 3D data 280 from one or more sensors in sensor system 120. The sensors can include Light Detection and Ranging (LIDAR) sensors (see Element 124 in FIG. 1), a set of stereo cameras, Red Green Blue Depth (RGB-D) sensors, radar sensors (see Element 123 in FIG. 1), or a combination of one or more of these types of sensors or other sensors capable of capturing 3D data.

In the embodiment of FIG. 12, 3D-data segmentation module 220 identifies 3D boundary information in the 3D data 280 derived from a point-cloud cluster, as discussed above. Examples of 3D boundary information include, without limitation, a convex hull, a voxelization, a non-convex hull, a bounding box, and mesh data.

In this embodiment, as in other embodiments described above, image segmentation module 240 identifies, in the 2D image data 290, 2D boundary information for an object. Examples of 2D boundary information include, without limitation, a perspective bounding box (a pseudo-3D bounding box drawn in perspective), a shape estimate (also pseudo-3D boundary information drawn in perspective), and a shape estimate with an accompanying pose estimate. FIGS. 7 and 8 illustrate examples of, respectively, perspective bounding boxes and shape estimates. As discussed above, image segmentation module 240 can employ a variety of techniques to perform object detection or boundary estimation in 2D image space. One well-known object-detection algorithm is MaskRCNN. That algorithm or other algorithms known to those skilled in the machine-vision art can be employed to produce a shape estimate or contour for an object.

As explained above, in some embodiments, 3D/2D registration system 170 includes a pose-estimation algorithm that estimates the direction in which an object in 2D image data 290 is oriented. In those embodiments, the pose estimate of the object can be used to aid registration, in 3D space, of a projected shape estimate with a 3D segment.

FIG. 13 is a flowchart of a method 1300 for registering 3D data with 2D image data, in accordance with another illustrative embodiment of the invention. Method 1300 will be discussed from the perspective of 3D/2D registration system 170 in FIG. 12. While method 1300 is discussed in combination with 3D/2D registration system 170, it should be appreciated that method 1300 is not limited to being implemented within 3D/2D registration system 170, but 3D/2D registration system 170 is instead one example of a system that may implement method 1300.

At block 1110 (in FIG. 13), 3D/2D registration system 170 (in FIG. 12) receives 3D data 280 from one or more sensors in sensor system 120. The sensors can include LIDAR sensors, a set of stereo cameras, RGB-D sensors, radar sensors, or a combination of one or more of these types of sensors or other sensors capable of capturing 3D data. At block 1120, 3D/2D registration system 170 receives 2D image data 290 from one or more cameras 126 that are part of sensor system 120. At block 1310, 3D-data segmentation module 220 identifies 3D boundary information in the 3D data 280. Examples of 3D boundary information include, without limitation, a convex hull, a voxelization, a non-convex hull, a bounding box, and mesh data.

At block 1150, image segmentation module 240 identifies, in the 2D image data 290, 2D boundary information for an object. Examples of 2D boundary information include, without limitation, a perspective bounding box (a pseudo-3D bounding box drawn in perspective), a shape estimate (also pseudo-3D boundary information drawn in perspective), and a shape estimate with an accompanying pose estimate. Examples of perspective bounding boxes and shape estimates, respectively, are illustrated in FIGS. 7 and 8.

At block 1320, integration module 260 projects the 2D boundary information into 3D space. At block 1330, integration module 260 performs shape matching between the projected 2D boundary information and the 3D boundary information, as discussed above.

FIG. 1 will now be discussed in full detail as an example vehicle environment within which the system and methods disclosed herein may operate. In some instances, the vehicle 100 is configured to switch selectively between an autonomous mode, one or more semi-autonomous operational modes, and/or a manual mode. Such switching also referred to as handover when transitioning to a manual mode can be implemented in a suitable manner, now known or later developed. “Manual mode” means that all of or a majority of the navigation and/or maneuvering of the vehicle is performed according to inputs received from a user (e.g., human driver/operator).

In one or more embodiments, the vehicle 100 is an autonomous vehicle. As used herein, “autonomous vehicle” refers to a vehicle that operates in an autonomous mode. “Autonomous mode” refers to navigating and/or maneuvering the vehicle 100 along a travel route using one or more computing systems to control the vehicle 100 with minimal or no input from a human driver/operator. In one or more embodiments, the vehicle 100 is highly automated or completely automated. In one embodiment, the vehicle 100 is configured with one or more semi-autonomous operational modes in which one or more computing systems perform a portion of the navigation and/or maneuvering of the vehicle along a travel route, and a vehicle operator (i.e., driver) provides inputs to the vehicle to perform a portion of the navigation and/or maneuvering of the vehicle 100 along a travel route. Thus, in one or more embodiments, the vehicle 100 operates autonomously according to a particular defined level of autonomy. For example, the vehicle 100 can operate according to the Society of Automotive Engineers (SAE) automated vehicle classifications 0-5. In one embodiment, the vehicle 100 operates according to SAE level 2, which provides for the autonomous driving module 160 controlling the vehicle 100 by braking, accelerating, and steering without operator input but the driver/operator is to monitor the driving and be vigilant and ready to intervene with controlling the vehicle 100 if the autonomous module 160 fails to properly respond or is otherwise unable to adequately control the vehicle 100.

The vehicle 100 can include one or more processors 110. In one or more arrangements, the processor(s) 110 can be a main processor of the vehicle 100. For instance, the processor(s) 110 can be an electronic control unit (ECU). The vehicle 100 can include one or more data stores 115 for storing one or more types of data. The data store 115 can include volatile and/or non-volatile memory. Examples of suitable data stores 115 include RAM (Random Access Memory), flash memory, ROM (Read Only Memory), PROM (Programmable Read-Only Memory), EPROM (Erasable Programmable Read-Only Memory), EEPROM (Electrically Erasable Programmable Read-Only Memory), registers, magnetic disks, optical disks, hard drives, or any other suitable storage medium, or any combination thereof. The data store 115 can be a component of the processor(s) 110, or the data store 115 can be operably connected to the processor(s) 110 for use thereby. The term “operably connected,” as used throughout this description, can include direct or indirect connections, including connections without direct physical contact.

In one or more arrangements, the one or more data stores 115 can include map data 116. The map data 116 can include maps of one or more geographic areas. In some instances, the map data 116 can include information or data on roads, traffic control devices, road markings, structures, features, and/or landmarks in the one or more geographic areas. The map data 116 can be in any suitable form. In some instances, the map data 116 can include aerial views of an area. In some instances, the map data 116 can include ground views of an area, including 360-degree ground views. The map data 116 can include measurements, dimensions, distances, and/or information for one or more items included in the map data 116 and/or relative to other items included in the map data 116. The map data 116 can include a digital map with information about road geometry. The map data 116 can be high quality and/or highly detailed.

In one or more arrangement, the map data 116 can include one or more terrain maps 117. The terrain map(s) 117 can include information about the ground, terrain, roads, surfaces, and/or other features of one or more geographic areas. The terrain map(s) 117 can include elevation data in the one or more geographic areas. The map data 116 can be high quality and/or highly detailed. The terrain map(s) 117 can define one or more ground surfaces, which can include paved roads, unpaved roads, land, and other things that define a ground surface.

In one or more arrangement, the map data 116 can include one or more static obstacle maps 118. The static obstacle map(s) 118 can include information about one or more static obstacles located within one or more geographic areas. A “static obstacle” is a physical object whose position does not change or substantially change over a period of time and/or whose size does not change or substantially change over a period of time. Examples of static obstacles include trees, buildings, curbs, fences, railings, medians, utility poles, statues, monuments, signs, benches, furniture, mailboxes, large rocks, hills. The static obstacles can be objects that extend above ground level. The one or more static obstacles included in the static obstacle map(s) 118 can have location data, size data, dimension data, material data, and/or other data associated with it. The static obstacle map(s) 118 can include measurements, dimensions, distances, and/or information for one or more static obstacles. The static obstacle map(s) 118 can be high quality and/or highly detailed. The static obstacle map(s) 118 can be updated to reflect changes within a mapped area.

The one or more data stores 115 can include sensor data 119. In this context, “sensor data” means any information about the sensors that the vehicle 100 is equipped with, including the capabilities and other information about such sensors. As will be explained below, the vehicle 100 can include the sensor system 120. The sensor data 119 can relate to one or more sensors of the sensor system 120. As an example, in one or more arrangements, the sensor data 119 can include information on one or more LIDAR sensors 124 of the sensor system 120.

In some instances, at least a portion of the map data 116 and/or the sensor data 119 can be located in one or more data stores 115 located onboard the vehicle 100. Alternatively, or in addition, at least a portion of the map data 116 and/or the sensor data 119 can be located in one or more data stores 115 that are located remotely from the vehicle 100.

As noted above, the vehicle 100 can include the sensor system 120. The sensor system 120 can include one or more sensors. “Sensor” means any device, component and/or system that can detect, and/or sense something. The one or more sensors can be configured to detect, and/or sense in real-time. As used herein, the term “real-time” means a level of processing responsiveness that a user or system senses as sufficiently immediate for a particular process or determination to be made, or that enables the processor to keep up with some external process.

In arrangements in which the sensor system 120 includes a plurality of sensors, the sensors can function independently from each other. Alternatively, two or more of the sensors can work in combination with each other. In such a case, the two or more sensors can form a sensor network. The sensor system 120 and/or the one or more sensors can be operably connected to the processor(s) 110, the data store(s) 115, and/or another element of the vehicle 100 (including any of the elements shown in FIG. 1). The sensor system 120 can acquire data of at least a portion of the external environment of the vehicle 100 (e.g., nearby vehicles).

The sensor system 120 can include any suitable type of sensor. Various examples of different types of sensors will be described herein. However, it will be understood that the embodiments are not limited to the particular sensors described. The sensor system 120 can include one or more vehicle sensors 121. The vehicle sensor(s) 121 can detect, determine, and/or sense information about the vehicle 100 itself. In one or more arrangements, the vehicle sensor(s) 121 can be configured to detect, and/or sense position and orientation changes of the vehicle 100, such as, for example, based on inertial acceleration. In one or more arrangements, the vehicle sensor(s) 121 can include one or more accelerometers, one or more gyroscopes, an inertial measurement unit (IMU), a dead-reckoning system, a global navigation satellite system (GNSS), a global positioning system (GPS), a navigation system 147, and/or other suitable sensors. The vehicle sensor(s) 121 can be configured to detect, and/or sense one or more characteristics of the vehicle 100. In one or more arrangements, the vehicle sensor(s) 121 can include a speedometer to determine a current speed of the vehicle 100.

Alternatively, or in addition, the sensor system 120 can include one or more environment sensors 122 configured to acquire, and/or sense driving environment data. “Driving environment data” includes and data or information about the external environment in which an autonomous vehicle is located or one or more portions thereof. For example, the one or more environment sensors 122 can be configured to detect, quantify and/or sense obstacles in at least a portion of the external environment of the vehicle 100 and/or information/data about such obstacles. Such obstacles may be stationary objects and/or dynamic objects. The one or more environment sensors 122 can be configured to detect, measure, quantify and/or sense other things in the external environment of the vehicle 100, such as, for example, lane markers, signs, traffic lights, traffic signs, lane lines, crosswalks, curbs proximate the vehicle 100, off-road objects, etc.

Various examples of sensors of the sensor system 120 will be described herein. The example sensors may be part of the one or more environment sensors 122 and/or the one or more vehicle sensors 121. Moreover, the sensor system 120 can include operator sensors that function to track or otherwise monitor aspects related to the driver/operator of the vehicle 100. However, it will be understood that the embodiments are not limited to the particular sensors described.

As an example, in one or more arrangements, the sensor system 120 can include one or more radar sensors 123, one or more LIDAR sensors 124, one or more sonar sensors 125, and/or one or more cameras 126. In one or more arrangements, the one or more cameras 126 can be high dynamic range (HDR) cameras, infrared (IR) cameras and so on. In one embodiment, the cameras 126 include one or more cameras disposed within a passenger compartment of the vehicle for performing eye-tracking on the operator/driver in order to determine a gaze of the operator/driver, an eye track of the operator/driver, and so on.

The vehicle 100 can include an input system 130. An “input system” includes any device, component, system, element or arrangement or groups thereof that enable information/data to be entered into a machine. The input system 130 can receive an input from a vehicle passenger (e.g. a driver or a passenger). The vehicle 100 can include an output system 135. An “output system” includes any device, component, or arrangement or groups thereof that enable information/data to be presented to a vehicle passenger (e.g. a person, a vehicle passenger, etc.).

The vehicle 100 can include one or more vehicle systems 140. Various examples of the one or more vehicle systems 140 are shown in FIG. 1. However, the vehicle 100 can include more, fewer, or different vehicle systems. It should be appreciated that although particular vehicle systems are separately defined, each or any of the systems or portions thereof may be otherwise combined or segregated via hardware and/or software within the vehicle 100. The vehicle 100 can include a propulsion system 141, a braking system 142, a steering system 143, throttle system 144, a transmission system 145, a signaling system 146, and/or a navigation system 147. Each of these systems can include one or more devices, components, and/or combination thereof, now known or later developed.

The navigation system 147 can include one or more devices, sensors, applications, and/or combinations thereof, now known or later developed, configured to determine the geographic location of the vehicle 100 and/or to determine a travel route for the vehicle 100. The navigation system 147 can include one or more mapping applications to determine a travel route for the vehicle 100. The navigation system 147 can include a global positioning system, a local positioning system or a geolocation system.

The processor(s) 110, the 3D/2D registration system 170, and/or the autonomous driving module(s) 160 can be operably connected to communicate with the various vehicle systems 140 and/or individual components thereof. For example, returning to FIG. 1, the processor(s) 110 and/or the autonomous driving module(s) 160 can be in communication to send and/or receive information from the various vehicle systems 140 to control the movement, speed, maneuvering, heading, direction, etc. of the vehicle 100. The processor(s) 110, the 3D/2D registration system 170, and/or the autonomous driving module(s) 160 may control some or all of these vehicle systems 140 and, thus, may be partially or fully autonomous.

The processor(s) 110, the 3D/2D registration system 170, and/or the autonomous driving module(s) 160 can be operably connected to communicate with the various vehicle systems 140 and/or individual components thereof. For example, returning to FIG. 1, the processor(s) 110, the 3D/2D registration system 170, and/or the autonomous driving module(s) 160 can be in communication to send and/or receive information from the various vehicle systems 140 to control the movement, speed, maneuvering, heading, direction, etc. of the vehicle 100. The processor(s) 110, the 3D/2D registration system 170, and/or the autonomous driving module(s) 160 may control some or all of these vehicle systems 140.

The processor(s) 110, the 3D/2D registration system 170, and/or the autonomous driving module(s) 160 may be operable to control the navigation and/or maneuvering of the vehicle 100 by controlling one or more of the vehicle systems 140 and/or components thereof. For instance, when operating in an autonomous mode, the processor(s) 110, the 3D/2D registration system 170, and/or the autonomous driving module(s) 160 can control the direction and/or speed of the vehicle 100. The processor(s) 110, the 3D/2D registration system 170, and/or the autonomous driving module(s) 160 can cause the vehicle 100 to accelerate (e.g., by increasing the supply of fuel provided to the engine), decelerate (e.g., by decreasing the supply of fuel to the engine and/or by applying brakes) and/or change direction (e.g., by turning the front two wheels). As used herein, “cause” or “causing” means to make, force, compel, direct, command, instruct, and/or enable an event or action to occur or at least be in a state where such event or action may occur, either in a direct or indirect manner.

The vehicle 100 can include one or more actuators 150. The actuators 150 can be any element or combination of elements operable to modify, adjust and/or alter one or more of the vehicle systems 140 or components thereof to responsive to receiving signals or other inputs from the processor(s) 110 and/or the autonomous driving module(s) 160. Any suitable actuator can be used. For instance, the one or more actuators 150 can include motors, pneumatic actuators, hydraulic pistons, relays, solenoids, and/or piezoelectric actuators, just to name a few possibilities.

The vehicle 100 can include one or more modules, at least some of which are described herein. The modules can be implemented as computer-readable program code that, when executed by a processor 110, implement one or more of the various processes described herein. One or more of the modules can be a component of the processor(s) 110, or one or more of the modules can be executed on and/or distributed among other processing systems to which the processor(s) 110 is operably connected. The modules can include instructions (e.g., program logic) executable by one or more processor(s) 110. Alternatively, or in addition, one or more data store 115 may contain such instructions.

In one or more arrangements, one or more of the modules described herein can include artificial or computational intelligence elements, e.g., neural network, fuzzy logic or other machine learning algorithms. Further, in one or more arrangements, one or more of the modules can be distributed among a plurality of the modules described herein. In one or more arrangements, two or more of the modules described herein can be combined into a single module.

The vehicle 100 can include one or more autonomous driving modules 160. The autonomous driving module(s) 160 can be configured to receive data from the sensor system 120 and/or any other type of system capable of capturing information relating to the vehicle 100 and/or the external environment of the vehicle 100. In one or more arrangements, the autonomous driving module(s) 160 can use such data to generate one or more driving scene models. The autonomous driving module(s) 160 can determine position and velocity of the vehicle 100. The autonomous driving module(s) 160 can determine the location of obstacles, or other environmental features including traffic signs, trees, shrubs, neighboring vehicles, pedestrians, etc.

The autonomous driving module(s) 160 can be configured to receive, and/or determine location information for obstacles within the external environment of the vehicle 100 for use by the processor(s) 110, and/or one or more of the modules described herein to estimate position and orientation of the vehicle 100, vehicle position in global coordinates based on signals from a plurality of satellites, or any other data and/or signals that could be used to determine the current state of the vehicle 100 or determine the position of the vehicle 100 with respect to its environment for use in either creating a map or determining the position of the vehicle 100 in respect to map data.

The autonomous driving module(s) 160 either independently or in combination with the 3D/2D registration system 170 can be configured to determine travel path(s), current autonomous driving maneuvers for the vehicle 100, future autonomous driving maneuvers and/or modifications to current autonomous driving maneuvers based on data acquired by the sensor system 120, driving scene models, and/or data from any other suitable source. “Driving maneuver” means one or more actions that affect the movement of a vehicle. Examples of driving maneuvers include: accelerating, decelerating, braking, turning, moving in a lateral direction of the vehicle 100, changing travel lanes, merging into a travel lane, and/or reversing, just to name a few possibilities. The autonomous driving module(s) 160 can be configured can be configured to implement determined driving maneuvers. The autonomous driving module(s) 160 can cause, directly or indirectly, such autonomous driving maneuvers to be implemented. As used herein, “cause” or “causing” means to make, command, instruct, and/or enable an event or action to occur or at least be in a state where such event or action may occur, either in a direct or indirect manner. The autonomous driving module(s) 160 can be configured to execute various vehicle functions and/or to transmit data to, receive data from, interact with, and/or control the vehicle 100 or one or more systems thereof (e.g. one or more of vehicle systems 140).

Detailed embodiments are disclosed herein. However, it is to be understood that the disclosed embodiments are intended only as examples. Therefore, specific structural and functional details disclosed herein are not to be interpreted as limiting, but merely as a basis for the claims and as a representative basis for teaching one skilled in the art to variously employ the aspects herein in virtually any appropriately detailed structure. Further, the terms and phrases used herein are not intended to be limiting but rather to provide an understandable description of possible implementations. Various embodiments are shown in FIGS. 1-13, but the embodiments are not limited to the illustrated structure or application.

The flowcharts and block diagrams in the figures illustrate the architecture, functionality, and operation of possible implementations of systems, methods and computer program products according to various embodiments. In this regard, each block in the flowcharts or block diagrams may represent a module, segment, or portion of code, which comprises one or more executable instructions for implementing the specified logical function(s). It should also be noted that, in some alternative implementations, the functions noted in the block may occur out of the order noted in the figures. For example, two blocks shown in succession may, in fact, be executed substantially concurrently, or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved.

The systems, components and/or processes described above can be realized in hardware or a combination of hardware and software and can be realized in a centralized fashion in one processing system or in a distributed fashion where different elements are spread across several interconnected processing systems. Any kind of processing system or another apparatus adapted for carrying out the methods described herein is suited. A typical combination of hardware and software can be a processing system with computer-usable program code that, when being loaded and executed, controls the processing system such that it carries out the methods described herein. The systems, components and/or processes also can be embedded in a computer-readable storage, such as a computer program product or other data programs storage device, readable by a machine, tangibly embodying a program of instructions executable by the machine to perform methods and processes described herein. These elements also can be embedded in an application product which comprises all the features enabling the implementation of the methods described herein and, which when loaded in a processing system, is able to carry out these methods.

Furthermore, arrangements described herein may take the form of a computer program product embodied in one or more computer-readable media having computer-readable program code embodied, e.g., stored, thereon. Any combination of one or more computer-readable media may be utilized. The computer-readable medium may be a computer-readable signal medium or a computer-readable storage medium. The phrase “computer-readable storage medium” means a non-transitory storage medium. A computer-readable storage medium may be, for example, but not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any suitable combination of the foregoing. More specific examples (a non-exhaustive list) of the computer-readable storage medium would include the following: a portable computer diskette, a hard disk drive (HDD), a solid-state drive (SSD), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or Flash memory), a portable compact disc read-only memory (CD-ROM), a digital versatile disc (DVD), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing. In the context of this document, a computer-readable storage medium may be any tangible medium that can contain or store a program for use by or in connection with an instruction execution system, apparatus, or device.

Program code embodied on a computer-readable medium may be transmitted using any appropriate medium, including but not limited to wireless, wireline, optical fiber, cable, RF, etc., or any suitable combination of the foregoing. Computer program code for carrying out operations for aspects of the present arrangements may be written in any combination of one or more programming languages, including an object-oriented programming language such as Java™ Smalltalk, C++ or the like and conventional procedural programming languages, such as the “C” programming language or similar programming languages. The program code may execute entirely on the user's computer, partly on the user's computer, as a stand-alone software package, partly on the user's computer and partly on a remote computer, or entirely on the remote computer or server. In the latter scenario, the remote computer may be connected to the user's computer through any type of network, including a local area network (LAN) or a wide area network (WAN), or the connection may be made to an external computer (for example, through the Internet using an Internet Service Provider).

The terms “a” and “an,” as used herein, are defined as one or more than one. The term “plurality,” as used herein, is defined as two or more than two. The term “another,” as used herein, is defined as at least a second or more. The terms “including” and/or “having,” as used herein, are defined as comprising (i.e. open language). The phrase “at least one of . . . and . . . ” as used herein refers to and encompasses any and all possible combinations of one or more of the associated listed items. As an example, the phrase “at least one of A, B, and C” includes A only, B only, C only, or any combination thereof (e.g. AB, AC, BC or ABC).

Aspects herein can be embodied in other forms without departing from the spirit or essential attributes thereof. Accordingly, reference should be made to the following claims rather than to the foregoing specification, as indicating the scope hereof. 

What is claimed is:
 1. A system for registering three-dimensional (3D) data with two-dimensional (2D) image data, the system comprising: one or more sensors to produce 3D data; one or more cameras to produce 2D image data; one or more processors; a memory communicably coupled to the one or more processors and storing: a 3D-data segmentation module including instructions that when executed by the one or more processors cause the one or more processors to identify, in the 3D data, a 3D segment; a data association module including instructions that when executed by the one or more processors cause the one or more processors to associate the 3D segment with an object; an image segmentation module including instructions that when executed by the one or more processors cause the one or more processors to identify 2D boundary information for the object in the 2D image data; a velocity estimation module including instructions that when executed by the one or more processors cause the one or more processors to determine a speed and a heading for the object; and an integration module including instructions that when executed by the one or more processors cause the one or more processors to register the 2D boundary information with the 3D segment by performing one of: shifting the 2D boundary information in 2D image space to a position that, based on the object's speed and heading, corresponds to a time at which the 3D data was captured, projecting the time-shifted 2D boundary information into 3D space, and matching the projected time-shifted 2D boundary information with the 3D segment; projecting the 2D boundary information into 3D space, shifting the projected 2D boundary information in 3D space to a position that, based on the object's speed and heading, corresponds to a time at which the 3D data was captured, and matching the time-shifted projected 2D boundary information with the 3D segment; and projecting the 2D boundary information into 3D space, shifting the 3D segment in 3D space to a position that, based on the object's speed and heading, corresponds to a time at which the 2D image data was captured, and matching the projected 2D boundary information with the time-shifted 3D segment.
 2. The system of claim 1, wherein the 2D boundary information is one of a bounding box, a perspective bounding box, a shape estimate, and a shape estimate with an accompanying pose estimate.
 3. The system of claim 1, wherein the 3D segment is 3D boundary information that includes one of a convex hull, a voxelization, a non-convex hull, a bounding box, and mesh data.
 4. The system of claim 1, wherein the 3D segment is a point-cloud cluster.
 5. The system of claim 1, wherein: the 2D boundary information is one of a perspective bounding box, a shape estimate, and a shape estimate with an accompanying pose estimate; the 3D segment is 3D boundary information that includes one of a convex hull, a voxelization, a non-convex hull, a bounding box, and mesh data; and the integration module includes instructions to perform one of: matching the projected time-shifted 2D boundary information with the 3D segment by performing shape matching between the projected time-shifted 2D boundary information and the 3D boundary information; matching the time-shifted projected 2D boundary information with the 3D segment by performing shape matching between the time-shifted projected 2D boundary information and the 3D boundary information; and matching the projected 2D boundary information with the time-shifted 3D segment by performing shape matching between the projected 2D boundary information and the time-shifted 3D boundary information.
 6. The system of claim 1, wherein the one or more sensors include at least one of a Light Detection and Ranging (LIDAR) sensor, a set of stereo cameras, a Red Green Blue Depth (RGB-D) sensor, and a radar sensor.
 7. The system of claim 1, wherein the velocity estimation module includes instructions to determine the speed and the heading for the object based on an analysis of the 2D image data.
 8. The system of claim 1, wherein the velocity estimation module includes instructions to determine the speed and the heading for the object based on an analysis of the 3D data.
 9. The system of claim 1, wherein the velocity estimation module includes instructions to determine the speed and the heading for the object based, at least in part, on information from a radar sensor.
 10. A method of registering three-dimensional (3D) data with two-dimensional (2D) image data, the method comprising: receiving 3D data from one or more sensors; receiving 2D image data from one or more cameras; identifying a 3D segment in the 3D data; associating the 3D segment with an object; identifying 2D boundary information for the object in the 2D image data; determining a speed and a heading for the object; and registering the 2D boundary information with the 3D segment by performing one of: shifting the 2D boundary information in 2D image space to a position that, based on the object's speed and heading, corresponds to a time at which the 3D data was captured, projecting the time-shifted 2D boundary information into 3D space, and matching the projected time-shifted 2D boundary information with the 3D segment; projecting the 2D boundary information into 3D space, shifting the projected 2D boundary information in 3D space to a position that, based on the object's speed and heading, corresponds to a time at which the 3D data was captured, and matching the time-shifted projected 2D boundary information with the 3D segment; and projecting the 2D boundary information into 3D space, shifting the 3D segment in 3D space to a position that, based on the object's speed and heading, corresponds to a time at which the 2D image data was captured, and matching the projected 2D boundary information with the time-shifted 3D segment.
 11. The method of claim 10, wherein the 2D boundary information is one of a bounding box, a perspective bounding box, a shape estimate, and a shape estimate with an accompanying pose estimate.
 12. The method of claim 10, wherein the 3D segment is 3D boundary information that includes one of a convex hull, a voxelization, a non-convex hull, a bounding box, and mesh data.
 13. The method of claim 10, wherein the 3D segment is a point-cloud cluster.
 14. The method of claim 10, wherein: the 2D boundary information is one of a perspective bounding box, a shape estimate, and a shape estimate with an accompanying pose estimate; the 3D segment is 3D boundary information that includes one of a convex hull, a voxelization, a non-convex hull, a bounding box, and mesh data; and the method includes performing one of: matching the projected time-shifted 2D boundary information with the 3D segment by performing shape matching between the projected time-shifted 2D boundary information and the 3D boundary information; matching the time-shifted projected 2D boundary information with the 3D segment by performing shape matching between the time-shifted projected 2D boundary information and the 3D boundary information; and matching the projected 2D boundary information with the time-shifted 3D segment by performing shape matching between the projected 2D boundary information and the time-shifted 3D boundary information.
 15. The method of claim 10, wherein the one or more sensors include at least one of a Light Detection and Ranging (LIDAR) sensor, a set of stereo cameras, a Red Green Blue Depth (RGB-D) sensor, and a radar sensor.
 16. The method of claim 10, wherein determining a speed and a heading for the object is based on an analysis of the 2D image data.
 17. The method of claim 10, wherein determining a speed and a heading for the object is based on an analysis of the 3D data.
 18. The method of claim 10, wherein determining a speed and a heading for the object is based, at least in part, on information from a radar sensor. 